Curse

JohnOo · Apr 16, 2006, 09:59 AM // 09:59

Guildwars randomly crashes on me with the well known message box "a serious error has occurred, please contact Anet" (or similair message).

I have been debugging the problem for some time now.

I already swapped the motherboard for a different brand and type, swapped graphics card, bought a new power supply (450W), tested harddisks, tested RAM (Corsair twinx 2048 MB 3200C2) over and over with no solution. I ran memtest86+ for hours and hours without any errors.

GW crashes at least about every hour with the "serious error has occurred, please send a report to Anet". The system is not overclocked and completely stable in 2d.

I am using latest drivers, bios, defragged the harddisk, increased virtual memory size to 2048-4096.

Also checked overheating: graphics card / processor etc are not getting too hot.

The graphics card is an Asus EN7800GT. Processor is an AMD 3800+ X2.

More system info:

CPU(s)
Number of CPUs 2
CPU#1 APIC ID = 0
Name AMD Athlon 64 X2 3800+
Code Name Manchester
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Family / Model / Stepping F B 1
Extended Family / Model F 2B
Brand ID 5
Package Socket 939
Core Stepping BH-E4
Technology 90 nm
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, SSE3, x86-64
CPU Clock Speed 2009.3 MHz
Clock multiplier x 10.0
HTT Bus Frequency 200.9 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 2009.3 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits
CPU#2 APIC ID = 1
Name AMD Athlon 64 X2 3800+
Code Name Manchester
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Family / Model / Stepping F B 1
Extended Family / Model F 2B
Brand ID 5
Package Socket 939
Core Stepping BH-E4
Technology 90 nm
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, SSE3, x86-64
CPU Clock Speed 2009.3 MHz
Clock multiplier x 10.0
HTT Bus Frequency 200.9 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 2009.3 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits

Mainboard and chipset
Motherboard manufacturer DFI Corp,LTD
Motherboard model LP NF4 Series, 1.0
BIOS vendor Phoenix Technologies, LTD
BIOS revision 6.00 PG
BIOS release date 06/23/2005
Chipset nVidia nForce4 rev. A3
Southbridge nVidia nForce4 MCP rev. A3
Sensor chip ITE IT8712
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16

Memory
DRAM Type DDR-SDRAM
DRAM Size 2048 MBytes
DRAM Frequency 200.9 MHz
FSB

RAM CPU/10
CAS# Latency 2.0 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 3 clocks
Cycle Time (TRAS) 6 clocks
Bank Cycle Time (TRC) 12 clocks
DRAM Idle Timer 256 clocks
Command Rate 1T
# of memory modules 2
Module 0 Corsair DDR PC3200 - 1024 MBytes
Module 1 Corsair DDR PC3200 - 1024 MBytes

Software
Windows version Microsoft Windows XP Professional Service Pack 2 (Build 2600)
DirectX version 9.0c

Has anyone got any idea how to fix this?

EternalTempest · Apr 17, 2006, 12:20 AM // 00:20

Have you tried re-installing GuildWars and trying the April version of Direct X and the most current Video/Sound card driver.

Zaxan Razor · Apr 17, 2006, 01:22 AM // 01:22

might be an idea to check what your firewall/anti-virus software is up to while gw is running.

lord_shar · Apr 17, 2006, 04:53 AM // 04:53

If reinstalling GW doesn't work, try running it from a different WinXP admin account and see what happens.

ange1 · Apr 17, 2006, 05:33 AM // 05:33

delete gw.exe and reinstall it

renoncour · Apr 17, 2006, 04:49 PM // 16:49

This might sound weird, but can you increase your RAM's voltage a notch in BIOS? I have 1GB of Corsair 3200 TwinX RAM, and I had all kinds of trouble with Guild Wars (and other games) until I upped the juice to 2.8V (up from 2.6V; I think the recommended is 2.75V). The memory didn't like the 2-3-3-6 timings until I did this. GW is rock-solid now though.

JohnOo · Apr 18, 2006, 08:05 AM // 08:05

I am running without a virusscanner and firewall now (just to test it), reinstalled windows and GW multiple times, am running with 2.8V on the DRAM, have latest directx and nvidia drivers installed. Still no solution.

ducktape · Apr 18, 2006, 09:02 PM // 21:02

Did you try downloading & running memtest86? If you are having any sort of memory issues you'll know after running that for a few hours. Looks like the most likely problem. You could also try a slower memory timing and see if that helps if you don't want to wait for the memtest.

Also, out of curiosity, when was the last time your Guild Wars worked, and have you changed anything (even programs) in your computer between then and when it broke?

JohnOo · Apr 19, 2006, 07:29 AM // 07:29

I already ran memtest for hours: no errors found. I have been having these errors for three months now: just after I bought a new PC.

QoH · Apr 19, 2006, 11:10 AM // 11:10

Try running latest 3dmark for 10++ hours.

cannonfodder · Apr 19, 2006, 02:44 PM // 14:44

Have you checked to see if there is an updated bios for your lanparty, the reason I say that is that some boards had problems with dual core processors, oh theres a thought have you installed the dual core processor driver from http://www.amd.com/us-en/Processors/..._13118,00.html

Try this. it may solve your problem.

EDit - I should read post fully, try the 64 bit processor driver.

JohnOo · Apr 20, 2006, 06:21 AM // 06:21

I already installed the processor driver and ran 3dmark for hours.

Mustache Mayhem · Apr 20, 2006, 08:09 AM // 08:09

renoncour has a good idea on what it sounds like.. usually those errors happen from memory (at stock speeds it's kinda hard to believe but maybe you have a weak stick)- with that dfi board the first thing I'd do is change my cas to 2.5 and run at 2T in the bios and see if that works.. if that does the trick you can bring it back down to 2 and 1T then increase the voltage until it's good or just leave it at 2.5.. it does'nt really make that much of a difference with the a64's.. thier memory controllers are so fast cas timing does'nt play a big role like it used to..

the other thing could be your ide or raid setup.. turn off dma transfers if the memory tweaks did'nt pan out.. other than that it's cooling- stock speeds the cpu should be fine- you can always install an external fan.. sinks on the memory could help if your running over stock voltage- other than that they are'nt really needed

hope it helps